Information on Demand Process Framework to Generate, Manage, Secure, and Deploy Browsers and Application Accessible Web Services

ABSTRACT

Disclosure is a method and system for delivering a reusable framework. The disclosure invokes an interface to define an information service within the reusable framework. The defined information service is stored in a repository. The method further includes outputting a service request as an address for invoking the defined information service and establishing a data connection after receiving the service request wherein the defined information service can be invoked.

FIELD OF THE INVENTION

Disclosure is a method and system for delivering a reusable framework.The disclosure invokes an interface to define an information servicewithin the reusable framework. The defined information service is storedin a repository. The method further includes outputting a servicerequest as an address for invoking the defined information service andestablishing a data connection after receiving the service requestwherein the defined information service can be invoked.

BACKGROUND

U.S. Patent 2005/0252194 application discloses a related user interface,or a component of a user interface that is deployed as a service in aservices oriented architecture for use, for example, in a dataintegration platform.

U.S. Patent Application 2006/0165040 discloses a communication system,method and standards for convergence solution to prevailingcommunication technologies & concepts includes rich client enabled,service oriented distributed information computation and communication(ICC) framework. The distributed network comprises of plurality ofclients at specified level of operation in the framework architectureessentially following TFHL networking standards for secured informationmanagement identified as NetAlter framework and said distributedframework (NetAlter) comprising of the Service Browser Application foraccessing the ICC framework contents in plurality of ways including peerto peer, offline, online etc. irrespective of operating system in useand location parameter.

The SOA Summit paper describes a self-service delivery solution that isbuilt on a service-oriented framework. The proposed solution is anintegration of assets and products based on a service orientedarchitecture (SOA) and Web services interfaces. The proposed solutionsupports the full life cycle of a service delivery from order placementthrough final reporting and billing.

SUMMARY OF THE INVENTION

An exemplary feature of this disclosure is a method of delivering areusable framework. The method consists of invoking an interface todefine an information service, storing the defined information servicein a repository, outputting a service request as an address for invokingthe defined information service, and establishing a data connectionafter receiving the service request wherein the defined service can beinvoked as part of the reusable framework.

A further exemplary feature of this disclosure is a method that returnsresults of data to a data request end-point in format specified in thedefined information service as part of the reusable framework.

Another exemplary feature of this disclosure is a method that invokesthe interface in a service oriented architecture as part of the reusableframework

Yet another exemplary feature of this disclosure is a method which addsadditional functionality to the results of data to allow for new dataformats as part of the reusable framework.

Another exemplary feature of this disclosure is a method which storesthe defined information service in a metadata repository as part of thereusable framework

A further exemplary feature of this disclosure is a method which definesthe defined service as a web service as part of the reusable framework.

Yet another exemplary feature of this disclosure is a method where acontroller receives the data service request, a service controller whichparses the data service request, the service controller references thedefined information service, and the service controller packages andbrokers resulting information from the data service request and thereferenced the defined information service to a routing module as partof the reusable framework.

Another exemplary feature of this disclosure is a method of enabling aservices oriented architecture to return the results of the data to thedata request end-point in the format specified in the definedinformation service as part of the reusable framework.

Another exemplary feature of this disclosure is a method of determiningrequired security in the defined information service and implementingthe required security as part of the reusable framework.

Yet another exemplary feature is a method of accessing multiple datasources in the reusable framework.

Yet another exemplary feature is a method of defining the definedinformation service using non-computer coded parameters in the reusableframework.

Another exemplary feature is a method of creating a standard messagemapping of messages in the reusable framework.

Still another exemplary feature is a method of logging the data servicerequests in a reusable framework.

Various other features, exemplary features, and attendant advantages ofthe present disclosure will become more fully appreciated as the samebecomes better understood when considered in conjunction with theaccompanying drawings, in which like reference characters designate thesame or similar parts throughout the several views.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features, aspects, and advantages will be betterunderstood from the following non-limiting detailed description ofpreferred embodiments of the disclosure with reference to the drawingsthat include the following:

FIG. 1 illustrates an overall flow of a logical environment forautomatic generation of information services from an end-user andservice creator perspective.

FIG. 2 illustrates service generation in which service parameters andfunctions are defined.

FIG. 3 illustrates a service controller in a reusable frameworkaccording to an embodiment of the present disclosure.

FIG. 4 illustrates a service routing module in a reusable frameworkaccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Within the current business climate there is a voracious demand forinformation to help improve operations, save money and increase revenue.This demand rises from all aspects of commerce, spans all geographiclocations and includes many methods of information distribution. Dataalone is not enough to drive the needs of growing businesses, this dataneeds to be made into actionable information and be delivered to theright people at the right time. In order to achieve the previouslystated goals information assets need to be accessible, accurate, easilyunderstood, and be re-usable. These attributes significantly aid in anorganizations ability to compete in the marketplace.

Business domain knowledge must be transferred into structures that areusable by systems and people. Tools that analyze existing legacy datathat help determine its structure and purpose need to be implementedinto service environments. These tools_could analyze data andautomatically create usable interfaces that either system to system orend-users can interact with. Tools that apply search engine technologyto discover needed metrics from information repositories also need to beincorporated into the “information as a service” environment.

The ability to create information metrics based on a request by an enduser or system without pre-built results is also a criteria forinformation as a service. Information must also be secured in accordancebusiness rules and external rules. Being able to protect informationassets is as critical as being able to provide information. To trulybecome an “information as a service” provider especially coming from anon-service environment the enterprise needs to apply automatic datamining, automatic analysis and discovery to help create usableinformation.

Disclosed is a method and system for developing information on demandprocess framework to generate, manage, secure, and deploy browsers andapplication accessible web services to connect to distinct data sourcesas a middle-ware web services layer.

The disclosure delivers a re-usable framework that enables an end userto turn traditional “data access points” into web service functions withno code. These services are useable in applications and direct accessthrough browsers or client systems and can be embedded in situational,mashup and any web connected application. This framework leveragesmetadata, parameterization to allow an application environment to simplydefine a data connect, a request for services, embed sql to returnresult sets of information to requestors. These requesters can either beapplications, appliances, or end-users.

By implementing this framework, exposing traditional data as webservices is quick and easy. The disclosure helps to support theInformation On Demand Strategy and will help achieve revenue growth andoperational savings. The framework provides a fast a cost effectivemethods for converting legacy information environments into SOA and webservice enabled enterprise infrastructures.

FIG. 1 illustrates the information on demand framework to generate,manage, secure, and deploy browser and application accessible webservices. Proper execution of the described elements through theframework will enable the disclosure to bring services orientedarchitecture to traditional information technology. The framework wrapsan SOA layer around any data source regardless of hosting format. Theservices generated in this framework implements information as aservice. This framework effectively exposes traditional data as webservices and quickly enables an enterprise to leverage SOAimplementations. There is no coding needed to create a web servicewithin this disclosure. A user of the framework quickly creates aservice by supplying parameters using a graphical interface, uponcompleting the questions posed in the interface the services ready todeploy.

Now referring to FIGS. 1 and 2, illustrated are the processes andactivities associated with defining a web service 100. This processillustrates all the parameters and functions that are defined of theservice being constructed.

An individual needing to define a web service for a data or informationrequests invokes a web enabled service generation interface 2 via abrowser or client 1 connected the internet. Upon invoking the interface2 the user is presented with options to define the service usingEnglish-language parameters, non-computer coded instructions. As aresult, there is no coding needed to create a web service.

A user of the framework quickly creates a service by supplyingparameters 13 using a service generation interface 2 upon completing thequestions posed in the interface the services ready to deploy. Thefollowing information is collected to define the parameters andfunctions of the service being constructed: An Application identifiertag 14 used to denote an application name; ID Address number 15 forsystem identification; A textual description of the service 16 fordocumentation purposes; A source URI 17 to define the location of theservice; A source URI alias 18 in the event that there is a need to maskthe actual server address; The ability to select the appropriate“Service Routing Modules” 30; Definition area 19 to specify the actualdata required with the capability of adding filter parameters to makethe generated services reusable for differed data filter criteria;Security Authentication parameter 20 for LDAP validation, SecurityAuthorization parameter 21 for Entitlement to access specific data;Security Access Control Parameter 22; Standard Name Mapping 23 used forcommon message mapping; Row Tag Name 24 to specify a name tag for eachreturned row of information; Group Access Control List sources 25 tospecify secured user group access to the service being defined; ServiceCreator email address 26; The generated URL service call 27 to be usedin application; Address Identification Parameters 28 for the traditionaldata sources; and cross reference listing of every component that callsthe service 29 this gets updated after the service is deployed fortraceability. This service generation interface 2 masks the complexityin accessing and securing information assets to environments such assituational application construction frameworks.

Requests are made in the form of URLs that are originally defined withinthe user interface 2 component. The generated URLs contain parametersthat indicate the location of the service, security tokens and datafilters.

All information describing the generated service is stored in theMetadata Repository 3 this information in referenced when service callURL's are invoked into the framework. This framework leverages metadata3 parameterization to allow an application environment to simply definea data connect, a request for services, embed sql to return result setsof information to requestors 7. Parameters 13 are referenced usingdetailed information that is stored in the Metadata Repository 3. Thisrepository 3 contains and captures information which provides attributesneeded to automatically construct web services. The web services createdwith this disclosure request, extract and deliver information toconsumers and applications. The Metadata Repository 3 drives thecreation and behavior of the web services that are generated with thisdisclosure. A World Wide Web browser enabled application acts as aninterface into a metadata repository 3. This metadata repository 3contains and captures various parameters that instruct a series of APIto automatically construct web service calls to request, extract anddeliver information data assets to end consumers and applications. Theseconsumers and applications area connected to the World Wide Web.

Once parameters 13 are stored a series of processes are invoked toexecute information deliver in the form of isolated web services request4. The service request 4 is a web service call structured in the form ofa URL. This URL contains information that is parsed by the ServiceController 5. The URL services calls are either posted directly in anybrowser type or any client that is connected to the internet. Once theservice URL is posted on the interned the Service Controller 5 isalerted.

FIG. 3 illustrates a service controller 35 in a reusable frameworkaccording to an embodiment of the present disclosure. These services areuseable and reusable in applications and direct access through browsersor client systems and can be embedded in situational, mashup and any webconnected application. These requesters 4 of the reusable framework caneither be applications, appliances, or end-users.

The Service Controller 35 directs the process once the URL is invoked onthe web. The Service Controller 35 receives the URL or header 34 andparses out the information passed 36. The Service Controller 35 thensearches and references the Metadata 37. The Service Controller 35 thenacts as a broker to determine were the request needs to be routed.Determination paths include routing to specific Service Routing Modules44. The resulting information is then packaged 42 and brokered 43 to aspecific Service Routing Module 44. The Service Controller 35 isessentially a broker that determines the required security 39, thestructure of the service call 39, and Service Module Routing 39. TheService Controller implements any of the defined security such asauthentication 40 and entitlement 41, thus protecting access to theactual information to only authorized requests. This allows theframework to have the ability to secure and protect the information thatis being requested. Capabilities in security include authentication 40and authorization or entitlement 41. With authentication 41, thegenerated service can be directed to ensure that the user requestinginformation is a valid resource. Access control lists 25 can be appliedto specific services to secure information request by individuals, teamsand system resources.

Referring to FIG. 4, and to FIG. 1 again, once the Service Controller 5routes to the correct Service Routing Module 45, a data connection 47 isestablished, requests for data are made 46 and returned 50 back to therequesting end-point 49 in a format that is specified in the URL.Service Routing Modules 45 contain specific logic that organizes thetype of processing that needs to occur to complete the request. Theseformats may include XML; News feed formats, spreadsheets, text data,JavaScript Object Notation, or additional formats.

The architecture is configured to allow for new formats as they becomeavailable. In addition, new Service Routing Modules can be added forincreased functions, current functions include the ability to set upproxy servers, cluster additional servers for growth, and the ability toaccess different information sources. The Service Routing Modules alsoenable the SOA wrapper 48 around the traditional data informationsources, effectively getting access to the data, executing requests andreturning results of information via SOA service calls. The ServiceRouting Modules 48 wraps an SOA layer around any data source 8regardless of hosting format. The Service Routing Modules 48 can alsocreate proxies, execute logging, formats result sets, negotiates betweendifferent versions of information sources, The Service Routing Modules48 help to format requested formats.

Returned information via the service URL call is sent back to therequesting end-point 7.

Actual data or information sources 8, which can be in any format locatedanywhere on an internet network.

A Service Routing Module 6 creates a proxy server 9 to mask actualserver addresses and to cluster other servers for growth. The proxycomponent 9 helps to establish a common nomenclature and framework forintegrating this environment with other service providers which can beon any web infrastructure including intranet or internet environments.The service proxy 9 enables a central point with a common nomenclaturefor grouping and accessing these generated services with service thatare provide by external providers.

A standard mapping of messages 10 is created in the event that standardsare not implemented in message interactions. By creating this mappinginterface messages can be standardized with minimal impact to theframework, thus preserving generic capabilities.

Usage logging 11 tracks usage of this framework. Service calls aretracked to log usage, this could be used to charge back requestors forCPU and data access from a services oriented implementation.

Again referring to FIG. 1, the present disclosure allows for theclustering of other servers or service providers 12.

It is to be understood that the provided illustrative examples are by nomeans exhaustive of the many possible uses for my disclosure.

From the foregoing description, one skilled in the art can easilyascertain the essential characteristics of this disclosure and, withoutdeparting from the spirit and scope thereof, can make various changesand modifications of the disclosure to adapt it to various usages andconditions.

It is to be understood that the present disclosure is not limited to theembodiments described above, but encompasses any and all embodimentswithin the scope of the following claims:

1. A method of delivering a reusable framework, said method comprisingsteps of: invoking an interface to define an information service withinsaid reusable framework; storing said defined information service in arepository; outputting a service request as an address for invoking saiddefined information service; and establishing a data connection afterreceiving said service request wherein said defined information servicecan be invoked.
 2. The method of claim 1, further comprising the step ofreturning results of data to a data request end-point in formatspecified in said defined information service.
 3. The method of claim 1,further comprising the step of invoking said interface in a serviceoriented architecture.
 4. The method of claim 1, further comprising thestep of adding additional functionality to said results of data to allowfor new data formats.
 5. The method of claim 1, wherein said repositoryfurther comprises a metadata repository.
 6. The method of claim 1,wherein said method of defining a service further comprises the step ofdefining a web service.
 7. The method of claim 1, further comprising thesteps of: a controller receiving said service request; said servicecontroller parses said service request; said service controllerreferences said defined information service; and said service controllerpackages and brokers resulting information from said service request andsaid referenced said defined information service to a routing module. 8.The method of 7, wherein said routing module further comprises the stepof enabling a service oriented architecture to return said results ofsaid data to said data request end-point in said format specified insaid defined information service.
 9. The method of claim 1, furthercomprising the steps of: determining required security in said definedservice; and implementing said required security;
 10. The method ofclaim 1, wherein the method of establishing a data connection furthercomprises the step of accessing multiple data sources.
 11. The method ofclaim 1, further comprises the step of defining said information serviceusing non-computer coded parameters.
 12. The method of claim 1, furthercomprising the step of a creating a standard message mapping interface.13. The system of claim 1, further comprising the step of logging saidservice request.
 14. An system for a delivering a reusable framework,said system comprising: an interface to define an information servicewithin said reusable framework; a repository to store said definedinformation service; and a service controller operative to receive aservice request as an address for invoking said defined informationservice and establishes a data connection after receiving said servicerequest wherein said defined information service can be invoked.
 15. Thesystem of claim 14, wherein said service controller established saiddata connections through a routing module, said routing module returnsresulting data to a requesting end-point in format specified in saidservice request.
 16. The system of claim 15, wherein said routing moduleis further operative to add additional functionality to said results ofdata to allow for new data formats.
 17. The system of claim 14, whereinsaid repository further comprises a metadata repository.
 18. The systemof claim 14, wherein said service controller is further operative todefine a web service.
 19. The system of claim 14, wherein said servicecontroller is further operative to determine the required security leveland implementing said security level in said defined service.
 20. Thesystem of claim 15, wherein said routing module is further operative tocreate a proxy server.
 21. The system of claim 14, further comprising amessage mapping interface to standardize messages.
 22. The system ofclaim 15, wherein said routing module is further operative to log usageof said reusable framework.
 23. A program storage device readable by amachine, tangibly embodying a program of instructions executable by themachine to perform method steps for delivering a reusable framework, themethod comprising the steps of: invoking an interface to define aninformation service within said reusable framework; storing said definedinformation service in a repository; outputting a service request as anaddress for invoking said defined information service; and establishinga data connection after receiving said service request wherein saiddefined information service can be invoked.
 24. The program storagedevice of claim 23, further comprising the step of returning results ofdata to a data request end-point in format specified in said definedinformation service.